<!DOCTYPE html>
<meta charset="utf-8">
<title>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</title>
<style>
  .a  { background: lightgreen }
  .d  { background: lightblue  }
  .r  { background: orange     }
  .fo { background: red        }
  .open   { border: solid red; padding: 0.2em; }
  :target { box-shadow: 0.25em 0.25em 0.25em;  }
</style>

<h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>

<p>Review document: <a href="https://www.w3.org/TR/2018/CR-css-writing-modes-3-20180524/">https://www.w3.org/TR/2018/CR-css-writing-modes-3-20180524/</a>

<p>Editor's draft: <a href="http://dev.w3.org/csswg/css-writing-modes-3/">http://dev.w3.org/csswg/css-writing-modes-3/</a>

<p>The following color coding convention is used for comments:</p>

<ul>
 <li class="a">Accepted or Rejected and positive response
 <li class="r">Rejected and no response
 <li class="fo">Rejected and negative response
 <li class="d">Deferred
 <li class="oi">Out-of-Scope or Invalid and not verified
</ul>

<p class=open>Open issues are marked like this</p>

<p>An issue can be closed as <code>Accepted</code>, <code>OutOfScope</code>,
<code>Invalid</code>, <code>Rejected</code>, or <code>Retracted</code>.
<code>Verified</code> indicates commentor's acceptance of the response.</p>
        <pre class='a' id='issue-1'>
Issue 1. <a href='#issue-1'>#</a>
Summary:  White space processing in text-combine-horizontal
From:     Yuki Seikguchi
Comment:  <a href='https://lists.w3.org/Archives/Public/www-style/2018Aug/0011.html'>https://lists.w3.org/Archives/Public/www-style/2018Aug/0011.html</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4139#issue-470826243'>https://github.com/w3c/csswg-drafts/issues/4139#issue-470826243</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-513589921'>https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-513589921</a>
Closed:   Accepted (undefine in L3, solve in L4)
Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209'>https://github.com/w3c/csswg-drafts/issues/4139#issuecomment-514701209</a></pre>
<pre class=' open' id='issue-2'>
Issue 2. <a href='#issue-2'>#</a>
Summary:  Need to be clear about inputs to computation of min-content, max-content, and fit-content sizes
From:     David Baron
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2890'>https://github.com/w3c/csswg-drafts/issues/2890</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420080835'>https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420080835</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420081451'>https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420081451</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420082478'>https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420082478</a>
Open</pre>
<pre class='a' id='issue-3'>
Issue 3. <a href='#issue-3'>#</a>
Summary:  Does vertical writing mode of an HTML body element cause an orthogonal flow?
From:     Nao Toyama
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3066'>https://github.com/w3c/csswg-drafts/issues/3066</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/3066#issuecomment-499111764'>https://github.com/w3c/csswg-drafts/issues/3066#issuecomment-499111764</a>
Response: <a href='https://github.com/w3c/csswg-drafts/pull/4130'>https://github.com/w3c/csswg-drafts/pull/4130</a>
Closed:   Accepted
Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/3066#issuecomment-499111764'>https://github.com/w3c/csswg-drafts/issues/3066#issuecomment-499111764</a></pre>
<pre class=' open' id='issue-4'>
Issue 4. <a href='#issue-4'>#</a>
Summary:  Define “fixed size” as used to determine available space of orthogonal flows
From:     Elika Etemad
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3095'>https://github.com/w3c/csswg-drafts/issues/3095</a>
Open</pre>
<pre class='a' id='issue-5'>
Issue 5. <a href='#issue-5'>#</a>
Summary:  Should writing-mode from display:contents element be applied to text?
From:     Xidorn Quan
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3176'>https://github.com/w3c/csswg-drafts/issues/3176</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/3176#issuecomment-425074813'>https://github.com/w3c/csswg-drafts/issues/3176#issuecomment-425074813</a>
Closed:   Retracted
Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/3176#issuecomment-425230949'>https://github.com/w3c/csswg-drafts/issues/3176#issuecomment-425230949</a></pre>
<pre class='oi' id='issue-6'>
Issue 6. <a href='#issue-6'>#</a>
Summary:  css-display-3 contradicts css-writing-modes-3
From:     prjnt
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3260'>https://github.com/w3c/csswg-drafts/issues/3260</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/3260#issuecomment-495363659'>https://github.com/w3c/csswg-drafts/issues/3260#issuecomment-495363659</a>
Closed:   OutOfScope
Resolved: Editor's discretion</pre>
<pre class='d' id='issue-7'>
Issue 7. <a href='#issue-7'>#</a>
Summary:  Improve old diagram in figure
From:     Nat McCully
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3439'>https://github.com/w3c/csswg-drafts/issues/3439</a>
Closed:   Deferred
Resolved: Editorial</pre>
<pre class='r' id='issue-8'>
Issue 8. <a href='#issue-8'>#</a>
Summary:  `unicode-bidi: plaintext` should affect list marker placement
From:     Ali Hardan
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3491'>https://github.com/w3c/csswg-drafts/issues/3491</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3491#issuecomment-453910610'>https://github.com/w3c/csswg-drafts/issues/3491#issuecomment-453910610</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3491#issuecomment-454207170'>https://github.com/w3c/csswg-drafts/issues/3491#issuecomment-454207170</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/3491#issuecomment-454256214'>https://github.com/w3c/csswg-drafts/issues/3491#issuecomment-454256214</a>
Closed:   Rejected
Resolved: Editor's discretion (<a href='https://github.com/w3c/csswg-drafts/issues/3491#event-2073586003)'>https://github.com/w3c/csswg-drafts/issues/3491#event-2073586003)</a></pre>
<pre class='a' id='issue-9'>
Issue 9. <a href='#issue-9'>#</a>
Summary:  Position of SVG text with writing-modes
From:     Evgeniy Reizner
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3504'>https://github.com/w3c/csswg-drafts/issues/3504</a>
Closed:   OutOfScope
Resolved: Editor's discretion (<a href='https://github.com/w3c/csswg-drafts/issues/3504#issuecomment-454254929)'>https://github.com/w3c/csswg-drafts/issues/3504#issuecomment-454254929)</a>
Verified: <a href='https://github.com/w3c/svgwg/issues/618#issuecomment-454397525'>https://github.com/w3c/svgwg/issues/618#issuecomment-454397525</a></pre>
<pre class='a' id='issue-10'>
Issue 10. <a href='#issue-10'>#</a>
Summary:  Clarify the baseline value during the top-to-bottom writing mode for Latin text
From:     Evgeniy Reizner
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3505'>https://github.com/w3c/csswg-drafts/issues/3505</a>
Response: <a href='https://github.com/w3c/svgwg/issues/629'>https://github.com/w3c/svgwg/issues/629</a>
Closed:   OutOfScope
Resolved: Editor's discretion (<a href='https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)'>https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)</a>
Verified: <a href='https://github.com/w3c/svgwg/issues/629#issuecomment-493824657'>https://github.com/w3c/svgwg/issues/629#issuecomment-493824657</a></pre>
<pre class='a' id='issue-11'>
Issue 11. <a href='#issue-11'>#</a>
Summary:  Abstract is slightly misleading
From:     Addisson Phillips
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3829'>https://github.com/w3c/csswg-drafts/issues/3829</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/pull/4132'>https://github.com/w3c/csswg-drafts/pull/4132</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513590636'>https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513590636</a>
Closed:   Accepted
Resolved: Editorial
Verified: <a href='https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513626272'>https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513626272</a></pre>
<pre class=' open' id='issue-12'>
Issue 12. <a href='#issue-12'>#</a>
Summary:  "calculations that require a definite available inline space" unclear
From:     David Baron
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4026'>https://github.com/w3c/csswg-drafts/issues/4026</a>
Open</pre>
<pre class='a' id='issue-13'>
Issue 13. <a href='#issue-13'>#</a>
Summary:  Vertical-align on table cells and writing-modes
From:     Florian Rivoal
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4033'>https://github.com/w3c/csswg-drafts/issues/4033</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-502581810'>https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-502581810</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511917326'>https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511917326</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511993353'>https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511993353</a>
Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511995790'>https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511995790</a>
Response: <a href='https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-513586713'>https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-513586713</a>
Closed:   OutOfScope
Resolved: Editor's discretion
Verified: <a href='https://github.com/w3c/csswg-drafts/issues/4033#event-2498263624'>https://github.com/w3c/csswg-drafts/issues/4033#event-2498263624</a></pre>
<script>
(function () {
    var sheet = document.styleSheets[0];
    function addCheckbox(className) {
        var element = document.querySelector('*.' + className);
        var label = document.createElement('label');
        label.innerHTML = element.innerHTML;
        element.innerHTML = null;
        var check = document.createElement('input');
        check.type = 'checkbox';
        if (className == 'open') {
            check.checked = false;
            sheet.insertRule('pre:not(.open)' + '{}', sheet.cssRules.length);
            check.onchange = function (e) {
                rule.style.display = this.checked ? 'none' : 'block';
            }
        }
        else {
            check.checked = true;
            sheet.insertRule('pre.' + className + '{}', sheet.cssRules.length);
            check.onchange = function (e) {
                rule.style.display = this.checked ? 'block' : 'none';
            }
        }
        var rule = sheet.cssRules[sheet.cssRules.length - 1];
        element.appendChild(label);
        label.insertBefore(check, label.firstChild);
    }
    ['a', 'd', 'fo', 'oi', 'r', 'open'].forEach(addCheckbox);
}());
</script>
